> Please don't implement your own custom "arena" or "memory pool" or "free list" - they will not be accepted.
> ...
> We ask that contributed programs not only give the correct result, but also use the same algorithm to calculate that result.
So there might not be too much room to improve. There could be some room to improve for things like "custom ... memory pool" since .NET Core has ArrayPool [2] built-in. But I can't tell if the spirit of that rule is "don't implement pooling" vs. "you can only allocate memory in the standard ways provided by the runtime."
> Please don't implement your own custom "arena" or "memory pool" or "free list" - they will not be accepted.
> ...
> We ask that contributed programs not only give the correct result, but also use the same algorithm to calculate that result.
So there might not be too much room to improve. There could be some room to improve for things like "custom ... memory pool" since .NET Core has ArrayPool [2] built-in. But I can't tell if the spirit of that rule is "don't implement pooling" vs. "you can only allocate memory in the standard ways provided by the runtime."
[1] http://benchmarksgame.alioth.debian.org/u64q/binarytrees-des...
[2] https://github.com/dotnet/corefx/blob/master/src/System.Buff...