do not interpret errors in return value of times() syscall

all return values are valid, and on 32-bit systems, values that look
like errors can and will occur. since the only actual error this
function could return is EFAULT, and it is only returnable when the
application has invoked undefined behavior, simply ignore the
possibility that the return value is actually an error code.

global cleanup to use the new syscall interface

misplaced & in times() made it fail to work, and clobber the stack

initial check-in, version 0.5.0