Lichtenberg v0.0.1; generates bare-bones coverage reports

Squashed commit of the following:

commit 65cad14558fb4b960b7adc0d366f8f08867ee5ce
Author: Ryan Muller <ryan@muller.io>
Date:   Sun Nov 30 23:09:09 2014 -0500

    Prepare for publishing!

commit cba3367bdb1eced399ee576e460ca116e67cdbc1
Author: Ryan Muller <ryan@muller.io>
Date:   Sun Nov 30 23:00:41 2014 -0500

    Finally managed to generate a sane coverage report!

commit 12e66fb0922fad4058971ae227170ab18ad9ac6e
Author: Ryan Muller <ryan@muller.io>
Date:   Sun Nov 30 22:37:17 2014 -0500

    Finally instruments a reasonable amount of the file!

commit a8209cc5e755bc4ba7e0f239e401d09a4db6ab50
Author: Ryan Muller <ryan@muller.io>
Date:   Sun Nov 30 19:48:47 2014 -0500

    Can't seem to figure out what's gobbling up my instrumentation!

commit cfeabf896ee5c6ce4cff6a98ace6d992862ae034
Author: Ryan Muller <ryan@muller.io>
Date:   Sun Nov 30 18:44:25 2014 -0500

    Targeting instrumentation propagation issue

commit dd05be4278f2b1361f84872c3f5ea2b6586f29ea
Author: Ryan Muller <ryan@muller.io>
Date:   Sun Nov 30 18:27:09 2014 -0500

    Fixed race condition in trace()

    Turns out it was caused by setTimeout(func, Math.random())
    ...well, that was foolish

commit e3458d38a932fdce7676ccef47bc1186def060ac
Author: Ryan Muller <ryan@muller.io>
Date:   Sun Nov 30 18:15:10 2014 -0500

    Outputs coverage results to test page

    Coverage results are currently useless though; they seem to be more the
    result of a race condition than the actual code coverage. Gotta dig
    deeper to find out what's going on here.

commit 48842370304e3097133fab5ed7c232a93cb2fc87
Author: Ryan A. Muller <ryan@muller.io>
Date:   Sun Nov 30 15:34:02 2014 -0500

    Started work on reporting functionality