Timestamps in nanoseconds

I'm submitting a

• feature request

Checklist

• Searched both open and closed issues for duplicates of this issue
• Title adequately and concisely reflects the feature or the bug

Information

sympact@0.0.3

The Problem

Timestamps are in ms (milliseconds). So, under certain circumstances, the difference between end and start is always zero ms. E.g: when profiling code that do not require long times to execute

Suggested solution

I would like to suggest timestamps in ns (nanoseconds). That could be achieved by replacing Date.now() for process.hrtime() in ./lib/profile.js. That would also require parsing the hrtime format with a function like this one:

function parseTime(hrtime) {
  return (hrtime[0] * 1e9) + hrtime[1]
}

Inspect the timestamp logic in the referenced profiler file, noting the issue links ./lib/profile.js while naming profiler.js, and review how Date.now() values are consumed. Replace millisecond timing with parsed process.hrtime() values so short profiling intervals are nonzero, then verify the reported start and end difference uses nanoseconds.