That's not true, conversion context is also used for deferred operations where it lives as long as the operation lives.
Depends on what you call briefly, but fine, it's still true for vast majority of use cases and it's still meaningless as a reason to change the code.
IMHO both using conversion context and `malloc` is fine in this case. I just don't see any reason to change between them.
The code also doesn't check for memory allocation failures
winevulkan was never consistent in memory allocation failures handling and changing that is more tricky than that. For this particular case, we don't need `malloc` to handle allocation failure.