Fixup for cycle RangeError invocation

From: #1183 :
Issue 9612: Cycle opSlice should throw when finish > start

Because a RangeError is not actually customizable, and the first argument is actually the file name. The error was producing:
```
core.exception.RangeError@2 > 1(3836): Range violation
```

Now it produces:
```
core.exception.RangeError@std\range.d(3835): Range violation
```