How to measure and diagnose performance issues in CoffeeScript applications

When working with CoffeeScript, I want to identify which parts of my code are slowing down execution. What measurement techniques or tools can I use to profile CoffeeScript after it has been compiled to JavaScript? For example, can I rely on console.time, benchmark.js, or Chrome DevTools, and how should I integrate them with the coffee -c compilation step?

Please outline a step‑by‑step process: write the CoffeeScript, compile it to JavaScript, run a benchmark script that measures specific functions, collect the timing data, and interpret the results to decide where to optimize. Include any caveats about source‑map support or differences CoffeeScript may introduce in the generated JavaScript.