opentelemetry-js-contrib: Inconsistent start and end time, startTime > endTime issues with express

What version of OpenTelemetry are you using?

$ npm list @opentelemetry/instrumentation-express   

test-obs@0.0.0 /Users/alexandre/Dev/Alteia/test-observability/test-obs
└─┬ @opentelemetry/auto-instrumentations-node@0.32.1
  └── @opentelemetry/instrumentation-express@0.31.1

What version of Node are you using?

$ node -v  
v16.17.0

Running on a M1 MacBook Pro

What did you do?

I am running a simple nest app to familiarize with open telemetry instrumentation and tooling. I have added the auto-instrumentation as mentioned in the docs, and running a custom nest app. After some times (especially If the Macbook go to sleep) I start to see such warning in the output :

Inconsistent start and end time, startTime > endTime [ 1664350641, 619671106 ] [ 1664350641, 619333687 ]

Jaeger traces looks completely wrong

What did you expect to see?

Here is the jaeger traces before the problem is appearing

What did you see instead?

The timing for the express span is getting completely off.

Additional context

I did a quick debugging session and source code analysis and I am very suspicious about the following code : https://github.com/open-telemetry/opentelemetry-js-contrib/blob/1c450f5fe31437aa7157ff6bb8602d330dc3b429/plugins/node/opentelemetry-instrumentation-express/src/instrumentation.ts#L266

https://github.com/open-telemetry/opentelemetry-js-contrib/blob/1c450f5fe31437aa7157ff6bb8602d330dc3b429/plugins/node/opentelemetry-instrumentation-express/src/instrumentation.ts#L274

It seems it is using a performance timer for the span end time, which may somehow differ from the wall time (https://github.com/open-telemetry/opentelemetry-js/issues/852 looks related), whereas other instrumentations does not override the span end time and works correctly in my case.