Every event Anvil captures gets richer context: how much memory the driver used before and after, how much CPU time the handler consumed, which controller model and OS version it's running on, and how long the controller has been up.

This runs for every event with essentially zero overhead. It's not something you turn on for a debugging session — it's always there.

Two concrete outcomes. First, memory leaks become visible: the event timeline picks up a slow, steady climb in memory that wouldn't otherwise be obvious, and flags the individual events allocating disproportionately. Second, when something is slow, you can tell what kind of slow it is — an event that spent 500ms inside your code is a different problem from an event that spent 500ms waiting on a network call.

Over time, the same data supports cross-cuts like "this driver behaves differently on an EA-1 vs an CORE 5" or "memory usage jumped after the Director 4.1 update".