The find dialog is dog slow !!!
After some usage, "Find" or "Find In Files" becomes very slow. I tried leaving the find box docked in the IDE window, but every time I type CTRL+F the dialog box goes into some sort of refresh seizure and only comes back after 3-4 seconds (on a 4 cores machine with 3GB of RAM 8).. an eternity if you are trying to jump somewhere in the code.
I noticed the same problem on a colleague's machine. I tried installing the SP1 beta for VS2008, which supposedly fixes some slowness in the GUI, but it didn't fix that one for sure.
An alternative is using CTRL+D (which I never really used before) to go to a quick find box, however that doesn't allow to change parameters such as case sensitivity and search for whole words, nor to verify what the current setting is.

Visual Studio has really become a piece of crap. It's still my favorite IDE ...if coupled with Visual Assist X. But if you program in C/C++, then you are a second class citizen, as Visual Studio has really sold its soul to the web/NET/database development or whatever else usage do most bored programmers out there.

One example is the dialog for changing syntax coloring. There is no more "C++ comment code". That is hidden behind "XML Comment" or something similar along those lines !

Another very sad thing, which has been worsening with years since Visual C++ 6, is the context help.
Theoretically one could press F1 on a keyword or API call and get the context help on it. In practice one presses F1, waits several seconds for some large application to load (or even to access the net !) and then gets a completely unrelated doc.. if lucky (one could set some sort of filters, but those never work right somehow).
For Windows API calls I used to get the Windows CE docs a few versions ago. Now I just get garbage.
Works much better by going on the MSDN web site and do a web search there.
How can possibly Microsoft win the web search engine battle if it can't even put together a system to help find a few thousands API calls ?

One last rant, if I'm allowed (I think I am !): headers have become completely unreadable. Microsoft includes and STL stuff are so complicated that give practically no help.
They must be machine generated.. would be nice to see the source of those.
MS includes have all sort of odd decoration to specify whether parameters are in input or output or what kind of passing they use.. turning those headers into something that could win an Obfuscated C Code Contest (for ugliness).

Thaaaaaaaannnkksss !!!