Composer And Travis Updates

PHPUnit4 made `strict` be even more strict :-D   That "risky" classification now means that any code that was executed by a test but was _not_ listed by `@covers` will result in the test being marked as "risky", which is nearly equivalent to a failure.  I guess it's supposed to force you into making your test cases even tighter with regard to the dependencies they touch.