Python coverage: (wrongly?) report a memory leak of type 'std::vector< std::shared_ptr< libcellml::AnalyserEquation > > *'

[agarny]

If we look at the latest Python coverage, we can see that it has 100% coverage, but swig/python detected a memory leak of type 'std::vector< std::shared_ptr< libcellml::AnalyserEquation > > *', no destructor found.

We don't have any memory leaks for our C++ codebase, so is that a false positive or a real issue with our Python bindings?

[nickerso]

Duplicate of #1129?

[hsorby]

Yes dupe.