#174 Fix our debugging to use VBTracer instead of our awful hack.

[Keith Gable]

Anyone who looks at our debug code will cry because
it's awful. It assumes that the socket subsystem has
been brought online and it assumes someone's online to
read it. It also prevents us from distributing an
official _debug build due to the sheer number of
SendSvrMsg calls happening.

Solution? vbAccelerator's VBTracer! We get rid of all
of our #If Debugging = 1 crap and just call Trace
"whatever". If you add TRACEMODE=1 to the project's
conditional compilation settings, it'll enable the
trace features. If not, Trace goes to the /dev/null in
the sky (except, whatever the hell the Windows
equavilent is... I forget.. NUL:? CON:? LPT1:?).

URL to article:
http://www.vbaccelerator.com/home/VB/Code/Techniques/RunTime_Debug_Tracing/article.asp

I wish SF had a "status whiteboard" so I can mark stuff
I want to target for 0.3.7. Anyways, this bug should
get fixed before 0.3.7. I know, I'm overdoing myself on
0.3.7...

{target-0.3.7}