Figure out caching issue

Some modules cached before semicov tries to load it. This behavior should be eliminated.

The issue mentions modules being cached before semicov loads them, which likely relates to Node.js module caching interfering with coverage instrumentation. Start by examining the main entry point (likely index.js or lib/semicov.js) and the module loading logic. Look for how semicov hooks into require() or uses tools like istanbul. Understanding the caching behavior and where to intercept module loading is key. A test demonstrating the issue would help verify a fix.

Scritto dal modello di indicizzazione a partire dal testo della issue.