DataGenerator moved into main
DataGenerator item size now instance-specific
Benchmark definitions centralized
Two-step data generation

This will allow future benchmarks to not be affected by the time it
takes to generate the data.
Use jmh to do some actual benchmarking
Don't benchmark KieBase creation.

Of course that this screwed up the results big time!
Tests are run on both engines

Shows some weir behavior.
Actually fill the session with facts

... which provides a nice explanation of why there was no difference
between Phreak and Rete-OO.
Reduce the data size for tests

And suddenly the hang is no longer there. It was never there, it just
takes so damn long on large data sets.
Measure what's important.
Better session acquisition.
add original phreak-examples project for reference
benchmark moved to separate module
benchmark - updated artifactId