NASL is not C so you can't introduce any memory leaks or similar
Any memory issue needs to be either fixed on scanner side (e.g. memory leaks, better memory management, ...) or solved via changes to the scan config (by e.g. the ones outlined in the parts above or by limit the concurrent scanned hosts and similar)
Pointing users to the vulnerability tests category won't help as these things can't be fixed/solved on VT side
What
See commit title
Why / Rationales
References
None