C# type safety when passing collections across the api surface

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Suggestion

some objects require a collection in their constructor and take ownership of the collection, such as objects in manifest.cs. this ticket is to fix type safety issues across the dll/pinvoke native interface so that developers do not make transcription mistakes when modifying the library code.

### Possible Implementation

_No response_

### Anything else?

_No response_

Start by reviewing manifest.cs and tracing the DLL/PInvoke native interface where collections cross the API boundary. Identify the collection ownership and type-safety mismatches described in the issue, then define the required changes so collection parameters are consistent and transcription mistakes are prevented across the interface.

Written by the indexing model from the issue text.