o_CopyTupleFromToCanDestroy

open override fun o_CopyTupleFromToCanDestroy(self: AvailObject, start: Int, end: Int, canDestroy: Boolean): A_Tuple

If a subrange ends up getting constructed from this object tuple then it may leak memory. The references that are out of bounds of the subrange might no longer be semantically reachable by Avail, but Java won't be able to collect them. Eventually we'll have an Avail-specific garbage collector again, at which point we'll solve this problem for real – along with many others, I'm sure.