w.r.t [1], Google has fixed #1, my biggest peeve of them all. Try searching for:

define:inulectable
or
define:hemifidl

Thanks!

However, i was able to find a somewhat petty inconsistency with their parser. Knowing that they have language design gurus on hand i'm always surprised at the ease with which you can contrive a test case based on their operators (recall my Google Print unearthing [2]). I think they spend about two seconds implementing the query parser, which is strange because entering queries is the Gateway Into Google.

Try searching for :

define:hemifidl | define:inulectable

You'll notice it corrects both of the words at once, singling out that "define" is an operator. However, when you go to search define is magically not an operator and you find yourself searching for the strange word "hemifield | define:ineluctable" (this works for any operator, i think)

And did anyone else notice they stopped pestering you about stop words? Try searching for:

of in on at to

[1] http://blogoscoped.com/forum/14069.html
[2] http://blogoscoped.com/archive/2005-12-08.html

ps, might want to update the docs:

http://www.google.com/support/bin/answer.py?answer=981
http://www.google.com/apis/reference.html#2_2

I bet updating documentation in so many languages is a real chore!

I think they got rid of stop words in 2005. At the latest it must have happened around September:
http://blogoscoped.com/archive/2005-09-29-n85.html