New benchmarks for a tokenizer I'm writing
Removing a dependency on Complexion from plugins

Previously the user would use

    tokenizer = new ComplexionSomething();

It was CompexionSomething's job to include Complexion.  Plugins also
couldn't extend others.  Now it looks a little different:

    tokenizer = new Complexion();
    tokenizer.plugin(ComplexionSomething());

ComplexionSomething still has to register itself with the tokenizer, but
does not need to modify prototypes or wrap Complexion in order to get
custom token objects inserted.  It is also easily possible to mock
Complexion and have CompexionSomething attach to the mock instead.  The
plugin can now use configuration like this:

    tokenizer = new Complexion();
    tokenizer.plugin(ComplexionSomething({
        someOption: true
    }));

It felt like the right thing to do in order to untangle dependencies.
Let me know if you have a better idea.
Fixing the example for the token factory
Updating tests so they work again
Removing addPlugin as there's really no need.

Just as good:

    var complexion = new Complexion();
    require('complexion-pascal')(complexion, {config:true});

Maybe I will make a convenience method in the future, but it will need
to eliminate more code than it generates.  :-)
Adding support for events including "start" and "end"
Releasing 0.1.1
Merge branch 'develop'