Original issue by @taniabogatsch

The allocation verification tag will be moved out of marcboeker#364, as it exceeds the scope of that PR.
It should be added again in a later PR.

Original comments

@taniabogatsch on 2025-02-26T13:21:00Z

marcboeker@c2c7dba

@taniabogatsch on 2025-05-15T10:00:06Z

I started working on this here: https://github.com/taniabogatsch/go-duckdb/tree/allocation-verification

But found that with the new instance cache changes, we'll always have an allocation exception - because the instance cache is kept alive indefinitely once created. I'll have to head over to duckdb-go-bindings, and change the allocation verification there.