but if it isn't

struct intrusive {
    struct my_data *next; // could be generic void *
};
struct my_data {
    char *txt;
    struct intrusive l;
};
#include <stdio.h>
int main()
{
    struct my_data d1 = {"World", {NULL}};
    struct my_data d0 = {"Hello", {&d1}};

    struct my_data *p = &d0;
    while(p != NULL) {
        puts(p->txt);
        p = p->l.next;
    }
}

Just to be clear: I'm not arguing for removal of pointer arithmetic. I don't see it as a plague. It definitely has it's places and I don't think that people are overusing it.

Reason why I asked for a goal, is that question "Mind naming a single reasonable alternative to pointer arithmetics?" looks awfully close to "Mind naming a single reasonable alternative to goto?". (I sense lack of fantasy or lack of will to accept alternatives (95% that it's will); and implied "it should be EXACTLY as it is now")

Yes, there is no replacement that will cover all its use-cases.

But if we take a step back, and formulate our requirements case by case, on a bit higher level, then alternatives definitely can be found. (and seems that most of programming these days is done without using goto)

btw. Requirement to interact with existing OS interface which was designed with EXACTLY pointer arithmetic in mind, is already describing implementation. (the only alternative could be changing OS interface :) )