Don't use Rake for the benchmarking scripts

This switches from using Rake to run the benchmark scripts to
just using ruby script files. This minimizes using Rake with the
gem and only requires it for gem building. I'd rather not rely on
extra dependencies that are not needed and for this case, Rake
isn't needed.

This removes the "run X requests against the Benchmark server"
functionality. This hasn't been used since DatTCP has been stable
and isn't related to "benchmarking". It was more of a system test
to see that everything worked for an echo server.
Merge pull request #39 from redding/jcr-dont-use-rake-for-bench

Don't use Rake for the benchmarking scripts
switch to the latest assert for test stubbing

The latest assert adds its own native stubbing API. The switches
to that. No behavior changes - just test cleanups.
Merge pull request #41 from redding/kr-assert

switch to the latest assert for test stubbing
Update the README to reflect the new DatTCP features

This updates the README to reflect the recent changes to DatTCP.
This includes changing the `Server` to a class from a module and
passing a block to `listen` to configure the TCP server. This
keeps the README relevant for reference when working with DatTCP.
Merge pull request #40 from redding/jcr-update-readme

Update the README to reflect the new DatTCP features
Minor cleanups

This is a couple minor cleanups. This switches the DatTCP logger
tests to use `UnitTests` instead of `BaseTests`. This also changes
from catching `Exception` to catching `StandardError`. These match
our latest conventions and best practices.