Another, more complicated instance of this is observable at http://www.google.com/search?q=nitty+gritty , where result #6 is: "Nitty gritty - Wikipedia, the free encyclopedia Wikipedia does not currently have an encyclopedia article for Nitty gritty. You may want to search Wiktionary for "Nitty gritty" instead. ..." If that were instead a redirect, Google could pick up the useful Wiktionary article rather than the useless Wikipedia page.
Yeah... that's far from ideal, but I don't think making them hard redirects would work well either, since it would make actually getting at the page within Wikipedia very difficult (unless you can get interwiki redirects to include a link back like intrawiki redirects do).
Another related issue is that redirects don't actually redirect - I certainly been confused at times by the URL in my address bar not actually being the URL for the page I'm looking at. Would it be good to actually use HTTP redirects? Possibly with a &redirectedfrom parameter in order to credit the link bank, if it can't be worked out from the referer or something. That would result in 2 requests to the servers rather than the current 1, but would allow links to be automatically updated by anything clever enough to know how to do that (for example, it should stop both the redirect and the real page appearing in Google with the same text, as I believe they do at the moment).