If I understand you correctly, you are talking about loading .dll dynamically in runtime.
So, It is matter of API calls. In Windows it is GetProcAddress and LoadLibrary API functions.
To use macro in order to replace one easy API call is strange and dirty solution IMHO.
What you actually want to achieve with this solution?

As I already said, you need to import directly only two functions from kernel32.dll - "LoadLibrary" and "GetProcAddress". Then use them with simple: invoke GetProcAddress, [dll_handle], strFunctionName
You simply do not need to develop new macros for this task.

If the obfuscation is a target of this exercise, how exactly it will work? If in debugger we simply can load a module with the API names and set a breakpoint onto an API entry (which returned by GetProcAddress) and debugger will stop there.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum