Access Violation Tracking

[Nikolay via Digitalmars-d-learn]

> i also developed a habit of writing assert()s before 
> dereferencing
> pointers first time (including class refs) in appropriate 
> places, so
> i'll got that stack trace for free. ;-) and i never turning off 
> that
> asserts in "release builds".

If we can't rely on system level may be we should have internal 
check for null deref like for array bounds?