Did you see a good perf improvement from using unsafe `slice_bytes` methods? I would have figured that the allocation going on would dominate the bounds checking.