I was mistaken. I was compiling my `seq` test with `-d:useMalloc` which fixes
the problem. Sorry..fiddling with too many knobs.
`string` and `seq[char]` behave identically with `gc:arc` and both get fixed
(139MB) with `--gc:arc -d:useMalloc`. Other GCs (including `none`) still beat
`gc:arc`-without-`useMalloc` on `string`. However, other gc's spend more memory
(like 420MB) than `gc:arc` on `seq[char]`. So, whatever is going on, `seq` is
actually worse than `string`, not better. { But also a side note for
@HashBackupJim to try `-d:useMalloc` with `--gc:arc`. }
At this point, I should raise an issue over at Github. I'll link it back here.
