You should try playing Losing Chess then: http://www.chessvariants.org/diffobjective.dir/giveaway.html

Not everybody will agree. One of the main advantages of std::list is splicing that can be done in O(1) if the size is not stored.

If the standard says it needs to be O(1) then you implement it that way and have a different list for fast splicing if needed.

Peter: Milton? Uh, could you turn that down just a little bit?

Milton: Uh, they said I could listen to the radio at a reasonable volume from nine to eleven while I'm collating….

Peter: But, no, no, no. I know you're allowed to, I was just thinking, like a personal favor, y'know?

Milton: I, I told Bill that if Sandra's going to listen to her headphones while she' working, I can listen to the radio while I'm collating...

Somewhat related: http://blog.regehr.org/archives/140

If he used wget (or similar utility) he could specify password as a command line argument. It's not a very good practice security-wise but people do this sometimes.

This requirement is only for other vendors to get the certification from Microsoft. Microsoft itself does not need to conform to it, so it is still possible that their products will be locked.

Not only straightforward, but also not novel. For example such lists have been described (with source code) in this textbook (published in 1994): Taming C++: Pattern Classes and Persistence for Large Projects by Jiri Soukup. Here's a picture taken from this book illustrating the concept: http://community.moertel.com/~thor/blog/pix-20061201/soukup-...