Const is inlined by the compiler and therefore must be set before compilation. Readonly can be set at runtime at instantiation.

I would think volatile can be used with a value type as it signifies that the value of the variable should not be placed in a register. It can be used instead of a lock construct, however they are not equivalent. I wouldn't trust a volatile when strict control over a shared variable is needed in a multithreaded app.

Would you ever need to use the fixed construct in a safe context? Its pretty much always used when p/invoking, which is not "safe".

Can't use a yield in an anonymous method... probably has something to do with the yield statement needing a strong rooting. Somebody whose IL is strong can answer that one.

Non question comments:

Indexers are pure joy. Never create a custom collection without one.

Richter says that you should always surround your arithmetic with checked and unchecked in order to communicate your overflow-checking intent to others who may read your code; I can't find much wrong with that.

If you create a DLL, you use (or should use!) internal to mark those classes and methods that users of your assembly should not access.

If you name a class in such a way that it masks a namespace, then you don't need the :: operator; you need a smack in the friggen head.

Wild, the page loads and eats my CPU, locking IE7 up tight. FF2, no problem.

Love the :: alias feature