I think OutOfMemory should not be restricted by nothrow, and I propose to solve it as described above.
More precisely: In principle, I think OutOfMemory *should* be restricted by nothrow, but it would break too much code, and be far too annoying, to be feasible. :)
Lars