Mapping Tamarin opcodes between C and Forth

So after a good time reading, I've figured out a little piece of how Forth hooks into the C. All the files discussed here are in the "core" directory of the tamarin-tracing folder. To make this easier to understand, we're going to use a specific example: the opcode "bitand". As defined in the avm2 pdf, the opcode is (bitand = 168 (0xa8)). Looking in vm.fs, we see that there is an extern keyword next to it:

EXTERN: OP_bitand            2toint & ibox NEXT ;


We also see that the actual "bitwise anding" is done in forth. If we look in vm_min.cpp we see this:
// OP_bitand offset=7175
SNEST, /* 2toint -29 */ 227, AND, LIT8, uint8_t(BoxedInt), SETRAWBOXTYPE, NEXT,

Looking for offset 7175 in the table below:
extern const short opcode_offsets[] = {
0, 0, 5, 6, 7, 1593, 2039, 2042,
2044, 2052, 0, 0, 2056, 2205, 2211, 2217,
2223, 2227, 2232, 2237, 2521, 2526, 2532, 2538,
2544, 2550, 2747, 2752, 2757, 2773, 2775, 3063,
3178, 3184, 0, 3190, 3285, 3286, 3287, 3293,
3299, 3303, 3304, 3305, 3306, 3307, 3308, 3309,
3317, 3322, 3330, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0,
3491, 3558, 4077, 4315, 4316, 4338, 4433, 4915,
4920, 4933, 4950, 0, 5097, 0, 5167, 5172,
0, 0, 0, 0, 0, 5177, 5182, 5187,
5207, 5272, 5280, 0, 0, 5294, 5903, 5913,
5928, 6028, 6072, 6073, 6074, 6078, 6085, 0,
6093, 0, 6141, 0, 6346, 6357, 6385, 6396,
6407, 6411, 6418, 6425, 6432, 6439, 6446, 6453,
6457, 0, 0, 0, 0, 0, 0, 0,
6458, 6462, 6469, 6470, 6477, 6484, 6488, 6668,
6699, 6706, 0, 0, 0, 0, 0, 0,
6713, 6721, 6731, 6746, 6756, 6771, 6853, 6861,
0, 0, 0, 0, 0, 0, 0, 0,
6869, 7104, 7112, 7120, 7128, 7137, 7155, 7165,
7175, 7182, 7189, 7196, 7203, 7210, 7218, 7226,

The bottom left entry, "7175" is at position (bitand = 168 (0xa8)) in the table. Also, looking at file: vm_min.h, we see extern_entry(OP_bitand, 7175). Since everything in forth is based on the address of a word, I think these offsets represent how far away from 0 each word is. It seems that the actual BINARY itself is a collection of jumps between forth words, and the order of the words are in vm_min.cpp. The actual implementation of these words are in vm.fs. Now as to why there are random numbers in vm_min.cpp, I am still lost. But at least now I have a footing.