@safe leak fix?

[Walter Bright]

grauzone wrote:
> Walter Bright wrote:
>> The code will be a little slower, but it will be memory safe. This 
>> change wouldn't be done in trusted or unsafe functions.
> That's just idiotic. One of the main uses of static arrays is to _avoid_ 
> heap memory allocation in the first place. Do what you want within 
> @safe,  but leave "unsafe" (oh god what a pejorative) alone.

Well, I did propose only doing this in safe functions!

Also, I agree with "unsafe" being a pejorative. Got any better ideas? 
"unchecked"?