Matcher finds slot start/end via odd means

We currently back up the current position by the tokenData length:
```go
startPos -= len(tokenData)
```

This is probably not entirely safe, and may lead to odd bugs. We should probably update the tokenizer to support fetching the last position, or potentially pass the last position through to matchExec so it can use that.