I recently noticed that tabread~ takes the floor of the requested table index, and since it's so easy to generate round off errors, e.g.
Annotation 2020-05-13 094610.png wouldn't it be a good idea to add 0.5 to any tabread~ indexing signal that you are using to access integer-indexed points of a table? Otherwise, depending on what arithmetic you happen to be doing at any given moment, tabread~ might return the point previous to the one you thought you were requesting.