Uninitialized vars in loop carried over to next iteration.

[Accensus]

Title sucks. Ran out of characters. Here's the situation:
Run the attached file and summon VarTest. The print result will be 0, 0, 1 for both the static and non-static calls. Array size will be 2. The correct and expected result is "0, 0, 0" with array size of 3.

Here are the two ways to "fix" this:
1. Uncomment the "Console.Printf(am.GetClassName());" lines. If something is referenced above the didInsert definition, the variable will be correctly initialized.
2. Explicitly initialize didInsert by setting it to false.

tl;dr something about the vars not being implicitly initialized.

[phantombeta]

This is caused by registers not being marked as dirty, so the local var init code thinks they're still clean and don't need to be implicitly initialized.
This is most likely going to be a pain in the ass to find every missing case of a missing dirty flag, so I'm personally not even touching this. If it just implicitly initialized anything without an initializer this wouldn't have ever happened, but y'know, possible microscopic performance losses were a bigger concern than ensuring safety here.
Oh, and by the way, this obviously means the uninitialized var reinterpret cast bug is still around, just harder to trigger.

[Graf Zahl]

Obviously this is just a bad coding example. Regardless of what a language does, you should never *ever* operate on uninitialized variables.