>>20
The major problems these days that crop up with optimizing C compilers reordering statements occur in multi-threaded, multi-core environments. In these environments, programming in assembly is only marginally better because the processor will reorder your stores and loads anyway.
If you look at Linux, memory ordering is handled by inserting different macros in your code. Depending on the processor, these will expand to "asm volatile ..." or "__asm__ __volatile__ ..." or whatever is necessary. The assembly instructions inside instruct the processor to be strict about some memory ordering, and the "volatile" keyword instructs the compiler to be strict.
You can't do that kinda shit in Java or C#. Not by a long shot. And you might as well use C, because C works, assembler takes way longer to write and maintain, and 90% of the programmers out there can't write assembler better than a C compiler anyway.
And the Java and Mono VMs are written mostly in C anyway, just like a good chunk of the C runtime is written in assembler. C won't go away because there's nothing to replace it.