Implemented delegate-based entity-updates for performance.

Lol, it actually works as I imagined. @main-- wanna profile?

This is a huge change, and actually I really hope that this works because
this would have some cool features. Main advantage: Not setting 1000s
of value in a slow-ass dictionary.

I've taken away support for the follwing features:
- Attribute weapons
- Bomb events

If you want fair comparison, profile master with
"DemoParser.AttributeWeapons" set to false. I really hope this is as fast
as I imagine!
Made the PropertyUpdateEventArgs generic.
Implemented feature to see if you've bound to the correct event-type

It is conditional, so it doesn't take away performance for "Release"
-builds.
Fixed bug discovered with the last commit.
Merge branch 'master' into nodict
[ci-skip] Added contribution guidlines.

Gimme ya pull-requests!
Never go full yolo

Checked the code 1337 times and didn't find bugs.
We can use travis to continuously verify that everything is fine,
so using the UnsafeBitstream for Release builds should be no problem.
Also: OMFG PERFORMANCE
Added Bitstream-Debugging

Just so we're _really_ safe and stuff like #15 can be detected earlier.
Restructured travis.yml commands

Also, added cleanup to detect timeouts
Fixed Abs of Vector, re-implemented bomb-events.
Splitting out verification should avoid timeouts
Print tick count during verification
'.' != '.\n'
Implemented base-classes and re-implemented weapon attribution.

In action: http://imgur.com/34dbUJ9
YOLODEBUG->DEBUG and other cleanups
Merge pull request #21 from moritzuehling/nodict

Created parsing of the packet-entities without huge dictionaries
You know you broke YoloDebug, @main--? YoloDebug is working again.

The Debug-Constant is defined here. I wonder why you check for this.
What else is the YOLO-Constant for...?
You know you broke *Release*, @moritzuehling?

rekt.
Revert fbf34e73cca7fb84cbefc379a9b1c6d7028a703b.
Kids these days

They be like "yo imma debuggin but YOLOLOLOLOLOLOL" and I'm just shaking my head

Alright, so I just reconstructed what happened:

 * It all started back in 97380783aef25671c0113a6e1e41f89fd1ca0650. Life was good, everyone was happy and a brave developer went on an adventure: He wanted to create a Yolo configuration.
 * He wrote some code and there was much rejoicing, as it all worked out according to his noble expectations.
 * But lo and behold! While he was enjoying the luxury of working code, 480e700bcc82c92f5fa622d14353cfedaf2ea974 sneaked into master, slipping right past his vigilant eyes that would usually watch the commit history!
 * And so it came about that YoloDebug was in master, but our unsuspecting hero still clueless!
 * Time passed and because it always worked so well, the people determined that the UnsafeBitstream shall be enabled by default for Release builds.
 * So the developer set out once again on a journey into the configuration profile files and fulfilled his duty.
 * He took his old paths and simply reversed most of his work, as he was sure that nobody had tampered with it. Just as he expected, he found the old code right there, just like he had left it long ago.
 * fd480ee23e5f43e295a767d2a614b21f2aaceb96 was conceived and everything seemed fine, so he returned back to the peaceful village.
 * He didn't notice the tiny little animal that infested the project that day: A bug.
 * Vigilant developer eyes had failed once and they failed again, as not even our hero's companion (ϰ intended) noticed the fatal combination.
 * Meanwhile, over in an entirely different, but similar universe (ohai bioshock infinite) called »ŋøðî¢ŧ«, the people saw YOLO and rejoiced. But due to insufficient swag, they built an even more wicked creation, one that the innocent protagonist could't even imagine in his wildest dreams: YOLODEBUG.
 * YoloDebug is a configuration while YOLODEBUG is a symbol that behaves kinda just like DEBUG
 * So our hero, warped over there for his next mission, wanted to defeat YOLODEBUG
 * 8a0cea6a177af3538b608de1fef78446f28f286c was the heroic battle. He received a severe blow to his head and while he prevailed, his genius didn't. Blinded by the horrors of preprocessors, he declared victory over YoloDebug, suddenly once again clueless about 480e700bcc82c92f5fa622d14353cfedaf2ea974, mere hours after he had discovered it.
 * Sometimes, the impossible happens. Sometimes, MIRACLES happen. Sometimes, git branches are merged. #21 in this case.
 * By accident, the protagonist's companion then wandered around and stumbled upon the animal that every developer fears. The one that had infested this codebase for such a long time. The bug.
 * In terror, he wanted to fix his code as quick as possible and conceived 51f9b6228e9f201b879714d14bba1a5d2a343415.
 * Our wise hero however saw the obvious implications of this change: Now Release builds used the ManagedBitstream! This conflicted with previous orders!
 * He stormed back to his toolbox, desparately trying to find what would restore things to a working state. And there was what he had been searching for: A spare OR operator. Thoroughly satisfied with this solution, he went back to the construction site and built fbf34e73cca7fb84cbefc379a9b1c6d7028a703b.
 * In this process, he remembered 480e700bcc82c92f5fa622d14353cfedaf2ea974 in dark and forgotten corners of his mind, but the injury was still deep, so he immediately for got about it *again*.
 * The companion was alarmed and slowly started to understand what had happened to his master. (ϰ <3)
 * He forced a magic potion called »¢ømmíŧ©òµm€nTß« down the hero's throat who then, finally and slowly, proceeded to awake from his feverish dreams.

TIL:

 * My memory is terrible
 * People overlook commits, multiple times
 * 480e700bcc82c92f5fa622d14353cfedaf2ea974 exists
 * Never begin commit messages with “you”.

Merry christmas. Or something like that.

/cc @moritzuehling