I would agree. Although my work involves writing some code under VS2010 on Windows so I can't use C++11 features, I still read Stroustrup's book. The tour of C++ is particularly helpful as it covers many of the new features, and offers tips like making the compiler work for you.
Stroustrup wrote an interesting paper (wish I could find it) in IEEE/Computer magazine that strongly advocated static code and not overuse of dynamic_casts etc. for speedy programs - this is making the compiler do all of the optimization instead of doing everything/making many decisions at run time.
The Wikipedia article on C++11 covers many of the new features quite well, but Stroustrup's recent revision of the C++ book is a joy to read - the fonts help, as the previous one had some pretty horrible fonts in my opinion.
VS2010 actually does implement quite a few of C++11's features, you have to be careful though and better read the MSDN documentation for each of them.
A weird case I found recently was that the VS2010 implementation of std::to_string(...) only supports long long, unsigned long long and long double.
http://msdn.microsoft.com/en-us/library/ee404875(v=vs.100).a...
Not very useful for most cases. Luckily VS2012+ supports the rest of the number types.
C++98 with TR1 comes close enough, it's what I use for lack of C++11 compiler support.
The funny thing is that "C++ as most people know it" is pretty far from "C++ as it was intended". Luckily, C++11 is nudging everyone towards the latter.
I was hating c++ for vague reasons I couldn't place. I was wrong.