Updated javadoc in Timer.Context.

Existing comment is a bit misleading, because the time "recording" is not "stopped" after calling the method, so multiple calls result in multiple updates from the same start time. At this point I don't consider that last part as a bug, but I think this behavior might be surprising if the user doesn't check actual implementation.

Please let me know what you think.