Yeah, that's what I figured. That's almost impossible for "safe" code to do in .NET. The only "unsafe" portions of the AI War are the ones that touch, via SlimDX, the DirectX components (and that's only because DirectX is "unsafe"). Please bear in mind that "safe" and "unsafe" might sound dangerous, but they are not. Rather, it refers to the execution isolation of the program, and the ability of the program to affect the system at large, if that makes sense.
Anyway, sounds like something might be up with your .NET runtime v2, or else potentially just something else on the computer interfered with it momentarily, or there's a very remote possibility it was related to AI War, but it wouldn't be my first thought with most .NET programs, honestly.
Thanks for posting the error -- hope that helps!