test(name, { timeout: 100 }, f(t) { ... }) gives incorrect timeouts.

When using the opts object with a timeout, it appears that the timeout is set at test load time, instead of test execution time. For large suites, this leads to spurious timeouts. The hack fix is to use t.timeoutAfter(100) instead.
