For applications with low expected item limits within taxonomies it can help to use a numeric id, combined with an open-ended rewrite of the user-readable content.
http://www.example.org/items/12-really-awesome-thing
RewriteRule ^/items/(\d+)[a-zA-Z0-9_\ -]+$ index.code?route=items&id=$1
Although you probably index your titles anyway, simple numeric key lookup makes the DB layer happy. Combine this with rel=canonical to your preferred url, and you can be more flexible with case, specific terms etc. It has the added bonus of reducing 404s through typo'd links and such.
A couple of other anecdotal points:
* Underscore is considered a letter, not a space, for most purposes
* Pages should either have a (faux) file extension, or no trailing slash. Reserve trailing slash for directories
* Rel Canonical also allows you to carry non-critical data in query string using [QSA] in the RewriteRule, without polluting the search index with duplicate content. Consider this for, example, default view of output (CD cover vs. title list)