When calculating request latency in an HTTP server, relying on non-standard properties like `req

When calculating request latency in an HTTP server, relying on non-standard properties like req.socket._start_time can lead to incorrect or missing timing data, especially in environments where the property is not defined. This can result in inaccurate latency metrics, which are critical for performance monitoring and debugging. The correct approach is to use standardized methods, such as tracking the start time using Date.now() at the moment the request is received, to ensure reliable and consistent timing measurements across different server setups.