It would be useful if there was a way to construct a VaList in such a way so that its lifecycle was bound to that of an existing native scope (as we do in other similar cases).