Totally fair points. I'm more of a programming language researcher, hence the interest in classification.
But yes, for production code it is totally the programmer's preference. I come from a background in game development. There are lots of times when game programmers won't trust new features or standard libraries. This is really a bad example of that, unless working with a compiler that doesn't support C++11 features, but it can be annoying when a lone programmer on a project starts using new features.
Anyway, there is a long history of trying to adopt a functional style to c++ in a way that makes sense for a static, weakly type language without garbage collection. After all, this is basically what the STL was all about.
Undoubtably using the modern c++ lambda can make this style of code clearer and better structured.
One could argue, I suppose, that it's still a bad approach - but it's not any easy argument in general.
Requiring first class functions to always be named isn't such a great idea (not speaking of c++ here), but it is true anonymous functions can be abused.