The garbage collector manages reachable managed memory. It doesn't decide when your application should finish with a report session, rented buffer, or operating-system handle. IDisposable gives the owner an explicit cleanup operation, and using ties that operation to a scope. Returning from the scope or throwing an exception still runs cleanup. Ownership is part of the contract. A wrapper should close a resource it owns, while a borrowed dependency keeps the lifetime chosen by its owner. Make Dispose idempotent so repeated calls don't repeat the cleanup. For a sealed class holding managed disposable children, a disposed flag and child cleanup are enough; it doesn't need a finalizer.
Use await using for IAsyncDisposable when cleanup itself must await work. The leases here are small test resources that expose acquisition and cleanup events. They don't open browser files or network connections, but the using statements and exception unwinding are the language's real behavior.
Each successful acquisition installs cleanup immediately. Async disposal is awaited before its scope completes.