Added the last of the unit test files from main.cpp

TODO:
1. make a test_all that includes all the unit tests
2. make changes to the test jamfile to use valgrind
3. make a bjam rule to pass via command line args to bjam to build either valgrind or regular unit tests
4. make a bjam rule to select all tests be run together or individually
5. remove main.cpp after this works
Begin creating test_all to run all the unit tests together
Missed a save on one of the test files
First try at running the new unit tests on travis

Broke the tests up into individual files, and updated the travis.yml to work with the new test setup

Some tests will fail, as there are a few linking issues, hopefully with the travis logs I'll be able to determine which ones.

TODO:
1. Fix linking/bulding errors
2. Troubleshoot the travis build
3. Figure how to get the valgrind flags into the unit tests (I tried, but don't think they work)
4. Make a rule or flag to build the right tests
5. Figure out how to build the tests with rules (This maybe uneccessary, but might be cleaner.
Fixed syntax error in travis.yml
Missed a define required for individual tests to run properly
Fixed an error in the signature of evil_random_file_io, and some things in the jamfile
Made it so all the tests will run
Added SpookyV2.cpp and its include directory to properly build the torture tests
Changes to Jamfiles and test_all.cpp to build properly

I had improperly linked one of the tests, so it failed

We should consider looking into a way to consolidate the test results at the end of the test run, rather that having pass/fail dispersed through the entire output. Maybe there is a facility in Boost.Build that can do that.
Fixed the linking for the actual tests rather than just the link tests

We're experienceing a wierd error in gcc where the filesystem is not being linked. Maybe there is some bad linking in the afio jamfile? We decalred a requirement for the projects in the unit tests to use afio, so it should link properly.

We'll need furthur investigation, tomorrow
Fixed the syntax errors in the unit test jamfile

Somehow I manged to fix the travis build by breaking the travis build.  :(
Gave all tests access to SpookyV2.cpp and its include directory

This links for me with GCC-4.8
Unit tests weren't being built with link=shared, so maybe that caused a problem on gcc-4.6?

This change didn't make a difference for me locally, but maybe it will fix things on travis.
fixed soem formatting in jamfile
Updated afio jamfile to match the one from MSVC_build branch.

Maybe these changes will benefit more than the msvc build of afio
Try to pass commandline args to valgrind

Previous attempts weren't working, maybe supplying the valgrind args to the run rule will work
Found a way to pass command line args to valgrind
Updated the logic of the unit test #includes and #defines to be more straighforward

Also updated jamfile
Fixed a syntax error in the unit test jamfile