It's not there for the simple reason that it's not in the win32 API, controls have an HWND (Window Handle given by the system) and an optional ID which is a numerical value between 0 and 32767. It can't be named and API calls rely on the HWND, not on the ID. The ID only serves internal dialog purposes to retrace a control HWND based on the known ID (for puristes, the ID is in fact stored as the MENU handle in child controls because they don't have menus)
In all the case, Khaled would need to implement en axtra mapping layer between control name and ID which I think is unecessary. If you can't cope with arranging your IDs (manage some ranges if you need expandible space) so there is no conflict, then I gues you shouldn't create and manage dialogs.
I don't know what the limit is in mIRC for IDs as maximum value, but just so you know, mIRC dialog IDs start at 6000 and not at 1. You use 1 in the dialog table but it's really 6001. That would mean that the upper limit is 32767 - 6000 for the max ID that can be used in mIRC.