Hi,
This is somewhat of a limitation of the way VisualGDB stores the remote directories. As they can be different for different hosts anyway, we would recommend opening the Makefile Settings page of VisualGDB Project Properties, changing something there (e.g. adding and removing space to CFLAGS) and pressing ‘Apply’. This will automatically redetect and re-configure the IntelliSense directories.
You can also try our new MSBuild backend in VisualGDB 5.2 (currently in Beta). It has a more automated way of dealing with remote include directories (you will still need to to click “repair MSBuild settings” after you change the alias target).