Sure

[humble valve]

If you disable burst and run again, you should get a better error message. As the error message alludes to, Burst can't do string interpolation for exception messages, so if you run without burst the {0} and {1} will be filled in with the correct index and length, and the callstack will show you which line is reading outside the range of the collection.

[random crater]

Without burst the error doesn't appear